Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error handling tutorial #3850

Merged
merged 3 commits into from
Jun 18, 2024
Merged

Error handling tutorial #3850

merged 3 commits into from
Jun 18, 2024

Conversation

adamw
Copy link
Member

@adamw adamw commented Jun 17, 2024

No description provided.

designated in the HTTP specification as "client errors".

On the other hand, there are "unexpected errors", that we didn't foresee. When they occur, they signal a bug in
the server's logic. When this happens, we should respond with a status code between 500 and 599, and log the error
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

suggestion: sometimes we return 503 when there are performance issues of our backend/infrastructure or a dependency, so it's not necessarily caused by a "bug", right?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ah yes, right. I'll mention this as well, thanks

@adamw adamw merged commit 08565af into master Jun 18, 2024
26 checks passed
@adamw adamw deleted the tutorial-errors branch June 18, 2024 09:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants